Computer methods and computer systems for automatic data analysis, reconcilliation and repair

ABSTRACT

In some embodiments, the instant invention includes a computer-implemented method that includes: specifically programming at least one computer system to perform: automatically obtaining input financial data; automatically determining units of work that the input financial data can be organized into; automatically importing the input financial data into a database based on the units of work; automatically validating the imported input financial data, by: identifying deficient units of work based on predefined rules, where each deficient unit of work has a current data error; analyzing, based on research information, the current data error to determine a current corrective action to remedy the current data error; and verifying that the current corrective action does not result in: an additional deficient unit of work, an additional data error, and a change in at least one predefined data report; and automatically executing the current corrective action to remedy the current data error.

RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.14/044,511; filed Oct. 2, 2013; entitled “COMPUTER METHODS AND COMPUTERSYSTEMS FOR AUTOMATIC DATA ANALYSIS, RECONCILIATION AND REPAIR”; whichis a continuation of U.S. patent application Ser. No. 13/861,258; filedApr. 11, 2013; entitled “COMPUTER METHODS AND COMPUTER SYSTEMS FORAUTOMATIC DATA ANALYSIS, RECONCILIATION AND REPAIR”; which claimspriority of U.S. Patent Appln. No. 61/622,976; filed Apr. 11, 2012;entitled “COMPUTER METHODS AND COMPUTER SYSTEMS FOR AUTOMATIC DATAANALYSIS, RECONCILIATION AND REPAIR,” which are incorporated herein byreference in their entirety for all purposes.

TECHNICAL FIELD

In some embodiments, the instant invention is related to data analysisand repair as part of data processing.

BACKGROUND

Typically, records of financial data (e.g., account data, transactionaldata) need to be verified or be reconciled against other financial datato confirm the correctness of the original financial data.

SUMMARY OF INVENTION

In some embodiments, the instant invention includes acomputer-implemented method that includes at least: specificallyprogramming at least one computer system to perform at least thefollowing: automatically obtaining input financial data from at leastone source; automatically determining a first plurality of units of workthat the input financial data can be organized into; automaticallyimporting the input financial data into at least one database based, atleast in part, on the first plurality of units of work; automaticallyvalidating the imported input financial data, where the validatingincludes at least: identifying, in the imported input financial data, asecond plurality of deficient units of work based on a third pluralityof predefined rules, where each deficient unit of work is a unit of workhaving at least one first current data error; analyzing, based at leastin part on research information in at least one first research database,the at least one first current data error to determine at least onefirst current corrective action to remedy the at least one first currentdata error, where the research information comprises historicalinformation about at least one first previous data error and at leastone first previous corrective action that remedied the at least onefirst previous data error; and verifying that the at least one firstcurrent corrective action does not result in at least one of: i) atleast one additional deficient unit of work, ii) at least one additionaldata error, and iii) at least one change in at least one predefined datareport; and automatically executing the at least one first currentcorrective action to remedy the at least one first current data error.

In some embodiments, each unit of work from the first plurality of unitsof work represents an account or a financial asset.

In some embodiments, the step of the automatically validating theimported input financial data can include segregating each deficientunit of work from the second plurality of deficient units of work intopredefined categories.

In some embodiments, the third plurality of predefined rules caninclude: i) at least one first standard rule that is a required rule,and/or ii) at least one optional rule.

In some embodiments, the third plurality of predefined rules includesrules associated with at least one of: i) position validation, ii) cashbalance validation, iii) data element validation, iv) securityvalidation, and v) posting considerations validation.

In some embodiments, the at least one first current data error ispersonal to a particular unit of work.

In some embodiments, the at least one first current data error isassociated with the common among the second plurality of deficient unitsof work.

In some embodiments, the step of the automatically validating theimported input financial data can further include: withholding fromposting each deficient unit of work for which a corrective action hasnot been determined.

In some embodiments, the step of the automatically validating theimported input financial data can further include: automatically markingeach deficient unit of work when posting the imported input financialdata so as to visually identify each deficient unit of work.

In some embodiments, the step of the automatically marking can furtherinclude: visually identifying each deficient unit of work based at leastin part on one of: i) at least one first type of data error, and ii) atleast one first pattern of data errors.

In some embodiments, the instant invention includes a computer systemthat includes at least the following components: a non-transient memoryhaving at least one region for storing computer executable program code;and at least one processor for executing the program code stored in thememory, where the program code includes at least: code to automaticallyobtain input financial data from at least one source; code toautomatically determine a first plurality of units of work that theinput financial data can be organized into; code to automatically importthe input financial data into at least one database based, at least inpart, on the first plurality of units of work; code to automaticallyvalidate the imported input financial data, where the code to validateincludes at least: code to identify, in the imported input financialdata, a second plurality of deficient units of work based on a thirdplurality of predefined rules, where each deficient unit of work is aunit of work having at least one first current data error; code toanalyze, based at least in part on research information in at least onefirst research database, the at least one first current data error todetermine at least one first current corrective action to remedy the atleast one first current data error, where the research informationcomprises historical information about at least one first previous dataerror and at least one first previous corrective action that remediedthe at least one first previous data error; and code to verify that theat least one first current corrective action does not result in at leastone of: i) at least one additional deficient unit of work, ii) at leastone additional data error, and iii) at least one change in at least onepredefined data report; and code to automatically execute the at leastone first current corrective action to remedy the at least one firstcurrent data error.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention will be further explained with reference to theattached drawings, wherein like structures are referred to by likenumerals throughout the several views. The drawings shown are notnecessarily to scale, with emphasis instead generally being placed uponillustrating the principles of the present invention. Further, somefeatures may be exaggerated to show details of particular components.

FIG. 1A and FIG. 1B form FIG. 1 that illustrates a schematic flowchartin accordance with some embodiments of the present invention.

FIG. 2A, FIG. 2B, and FIG. 2C form FIG. 2 that illustrates anotherschematic flowchart in accordance with some embodiments of the presentinvention.

FIG. 3 illustrates yet another schematic flowchart in accordance withsome embodiments of the present invention.

FIG. 4A and FIG. 4B form FIG. 4 that illustrates still yet anotherschematic flowchart in accordance with some embodiments of the presentinvention.

FIG. 5 illustrates a computer system in accordance with some embodimentsof the present invention.

FIG. 6 illustrates another computer system in accordance with some otherembodiments of the present invention.

FIG. 7 illustrates yet another schematic flowchart in accordance withsome embodiments of the present invention.

FIG. 8 illustrates still another schematic flowchart in accordance withsome embodiments of the present invention.

FIG. 9 illustrates yet another schematic flowchart in accordance withsome embodiments of the present invention.

The figures constitute a part of this specification and includeillustrative embodiments of the present invention and illustrate variousobjects and features thereof. In addition, any measurements,specifications and the like shown in the figures are intended to beillustrative, and not restrictive. Therefore, specific structural andfunctional details disclosed herein are not to be interpreted aslimiting, but merely as a representative basis for teaching one skilledin the art to variously employ the present invention.

DETAILED DESCRIPTION

Among those benefits and improvements that have been disclosed, otherobjects and advantages of this invention will become apparent from thefollowing description taken in conjunction with the accompanyingfigures. Detailed embodiments of the present invention are disclosedherein; however, it is to be understood that the disclosed embodimentsare merely illustrative of the invention that may be embodied in variousforms. In addition, each of the examples given in connection with thevarious embodiments of the invention which are intended to beillustrative, and not restrictive.

Throughout the specification and claims, the following terms take themeanings explicitly associated herein, unless the context clearlydictates otherwise. The phrases “In some embodiments” and “in someembodiments” as used herein do not necessarily refer to the sameembodiment(s), though it may. Furthermore, the phrases “in anotherembodiment” and “in some other embodiments” as used herein do notnecessarily refer to a different embodiment, although it may. Thus, asdescribed below, various embodiments of the invention may be readilycombined, without departing from the scope or spirit of the invention.

In addition, as used herein, the term “or” is an inclusive “or”operator, and is equivalent to the term “and/or,” unless the contextclearly dictates otherwise. The term “based on” is not exclusive andallows for being based on additional factors not described, unless thecontext clearly dictates otherwise. In addition, throughout thespecification, the meaning of “a,” “an,” and “the” include pluralreferences. The meaning of “in” includes “in” and “on.”

In addition, as used herein, the terms “real time” means without unduedelay and to be performed within a single time communication sessionwhile particular healthcare constituents transacting with or through atleast some embodiments of the computer systems of the instant invention.

In some embodiments, the instant invention provides a complex dataanalysis and repair tool that analyzes and repairs financial data aspart of data processing. In some embodiments, the data processing can bean Extract, Transform and Load (ETL) process that at least involves:

1) Extracting data from outside sources,

2) Transforming it to fit operational needs (which can include qualitylevels), and

3) Loading it into the end target (database or data warehouse).

In some embodiments, the instant invention uses business logic rules torecognize and repair financial data based on common irregularities foundin most financial data providers. In some embodiments, the instantinvention reconciles financial transactions in correlation to positionsand balances received by data providers. In the event financial datadoes not reconcile, or has any type of data integrity error, in someembodiments, the instant invention can then verify the data integrity onindividual records of data received from financial data vendors. In someembodiments, the instant invention provides a thorough validation ofeach record received from vendors through a rules based engine. In someembodiments, the instant invention, each record can/will have multiplechecks and the results of each validation will be stored for eachrecord. Upon failing a validation, in some embodiments, the instantinvention can attempt to perform a data repair based on business logicrules. In some embodiments, the instant invention records that fail thevalidation and data repair are not be loaded into the client database,instead those records are held in one or more interim database forfurther reviewed by highly trained individuals before being released tothe end user. In some embodiments, records that pass validation areloaded into the client's data warehouse.

In some embodiments, the instant invention is a part of an ETL processthat processes financial data, validates repairs and loads data that hasbeen received from various financial data providers:

Step 1: Validate the data

Step 2: Attempt to repair the data

Step 3: Load the data into the data warehouse

Step 4: Any data that failed a validation, hold in an interim databasefor manual and/or automatic review/repair before being released to enduser.

In some embodiments, the instant invention automatically repairs datathat does not pass data integrity checks, any undetected exceptions withdata integrity and can prepare data for manually review.

In some embodiments, the instant invention provides a flexible,rules-based, automated data scrubbing engine. In some embodiments, theinstant invention automatically identifies un-reconciled transactionsand missing data elements and applies fixes based at least in part on aconfigurable set of business logic rules by recognizing patterns byusing complex business logic housed in the data scrubbing engine.

In some embodiments, a manual data scrubbing service can be additionallyperformed. In some embodiments, all failed validations that cannot beautomatically corrected with the automated data repair engine can beheld from posting to the database until the failure is analyzed.

In some embodiments, the instant invention can be an integral part ofthe data processing shown in FIG. 1. For example, in some embodiments,the instant invention automatically identifies un-reconciledtransactions and missing data elements and applies fixes, when possible,based on a configurable set of business logic rules housed in one ormore databases associate with one or more data scrubbing engines.

In some embodiments, the instant invention provides a rules-based datascrubbing engine with aggregation capabilities. In some embodiments, theengine identifies un-reconciled positions, balance conditions, andvalidates specific elements of the custodial data. In some embodiments,failed validations are held from posting to the firm database untilbeing analyzed.

Examples of Data Validation Rules

In some embodiments, the instant invention can perform at least thefollowing types of validations:

-   -   Position Reconciliation. In some embodiments, this validation is        completed prior to posting data into the client database by        comparing data being received to the data currently in the        client database. In the event a discrepancy is found, the        account will be held until this position reconciles.    -   Balance Reconciliation. In some embodiments, Balance        Reconciliation compares balances received to balances currently        in the client database prior to posting them to the client        database.

In some embodiments, the instant invention can perform rules andvalidations on a Unit of Work level, for example, but not limited to, onan account or security. For example, if one position in an account doesnot balance, the entire account will be automatically held foranalysis/investigation/repair. In some embodiments, the instantinvention can, in real-time, flag Position or Balance records that areout of balance as well as dynamically mark them accordingly, regardingsuccess or failure, for each validation rule. In some embodiments, theinstant invention can then perform a dynamic repair process based onrecognized error(s) or error pattern(s) (e.g., a missing price on aMoney Market or a particular stock).

In some embodiments, the inventive systems and methods of the instantinvention can incorporate at least two sets of rules, optional andstandard, which can be used to ensure proper data quality as well asprovide a level of customization by the client. For example, theOptional Validation Rules can be enabled or disabled to suit theclient's needs and the Standard Validation Rules are required for datavalidation. Table 1 provides examples of the Optional Validation Rules.Table 2 provides examples of the Standard Validation Rules.

TABLE 1 VALIDATION RULE VALIDATION VALIDATION RULE CODE DESCRIPTION RULEDEFINITION BalanceReconcile Check Balance A Balance Does reconciles onNot Reconcile Account PositionReconcile Checks position Invalid Accountreconciliation on Position Account ReconciliationAccountRepAssignedToUser Verify the Representative RepresentafiveCodeCode not is assigned to a User Assigned to a UserAccountSignCheckMarketValue Verify Market Value is Invalid Marketcorrectly signed Value BalanceDateCheckEffectiveDate Verify EffectiveDate Effective Date is is no further than 2 Further than 2 months outMonths Out SecurityOptionSymbol Verify Symbol is Missing Symbolpopulated on option for Option securities SecurityTransactionDateCheckTransactionEffectiveDate Verify TransactionTransaction Effective Date is no Effective Date further than 2 Furtherthan 2 months out Months Out TransactionRegLine1OrAddrLine1PopulatedVerify that the Missing address RegLine1 or Addr line 1 Line1 ispopulated if the pTigershark field is enabledTransactionMoneyMarketIsPriced Verify transactions Money Market thathave an action Transaction is Not attribute of Priced “Reconcile” andsecurity type of “MoneyMarket” also are priced at 1

TABLE 2 VALIDATION RULE VALIDATION VALIDATION RULE CODE DESCRIPTION RULEDEFINITION AccountastodianChange Verify Account UOW Invalid Change ofdoes not have possible Custodian Custodian changeAccountDataTypeCheckCloseDate Verify data type Invalid Account CloseDate AccountDataTypeCheckOpenDate Verify data type Invalid Account OpenDate AccountDataTypeCheckPrimaryDOB Verify data type invalid AccountPrimary DOB AccountDataTypeCheckSecondaryDOB Verify data type invalidAccount Secondary DOB AccountDuplicateCheck Check for duplicateDuplicate Account account records AccountIDOnAccount Validates AccountUOW Missing Account AccountID is populated ID AccountIDOnBalanceValidates Balance UOW Missing Account AccountID is populated ID onBalance AccountIDOnCostBasis Validates CostBasis UOW Missing AccountAccountID is populated ID AccountIDOnObjective Validates Objective UOWMissing Account AccountID is populated ID on ObjectiveAccountIDOnPosition Validates Position UOW Missing Account AccountID ispopulated ID on Position AccountIDOnTransaction Validates TransactionMissing Account UOW AccountID is ID on Transaction populatedAccountNetworkLevelValid Verify NetworkLevelID is Missing Networkpopulated if Level ID NetworkLevel is provided AccountPrimarySSNCheckVerify Account columns invalid Primary are populated if the SSNbProcessTigershark flag is set to 1 AccountRepCodeValid Verify theRepresentative RepresentativeCode is Code not assigned to a UserAssigned to a User AccountRequiredFields Verify required fields areMissing Required populated Account informationAccountThirdPartyMoneyManager Verify if the Account has Missing Third athird party MM that the Party Money ID is set Manager IDAccountTypeCustodianValid Verify Missing CustodianAccountTypeCustodianID ID is populated if AccountTypeCustodian isprovided AccountTypeValid Verify AccountTypeID is Missing Accountpopulated if AcccountType Type ID is provided BalanceCustodianChangeVerify Balance UOW does Invalid Change of not have possible CustodianCustodian change BalanceDataTypeCheckEffectiveDate Verify data typeInvalid Balance Effective Date BalanceDuplicateCheck Check for duplicateDuplicate Account balance records Balance BalanceRequiredFields Verifyrequired fields are Missing Required populated Account Balanceinformation BalanceTypeValid Verify BalanceTypeID is Missing Balancepopulated if BalanceType Type ID is providedCostBasisDataTypeCheckCloseAmount Verifies Field is the invalid CostBasis proper data type Close Amount CostBasisDataTypeCheckCloseDateVerifies Field is the invalid Cost Basis proper data type Close DateCostBasisDataTypeCheckClosePrice Verifies Field is the invalid CostBasis proper data type Close Price CostBasisDataTypeCheckOpenAmountVerifies Field is the Invalid Cost Basis proper data type Open AmountCostBasisDataTypeCheckOpenDate Verifies Field is the Invalid Cost Basisproper data type Open Date CostBasisDataTypeCheckOpenPrice VerifiesField is the Invalid Cost Basis proper data type Open PriceCostBasisDataTypeCheckQuantity Verifies Field is the Invalid Cost Basisproper data type Quantity CostBasisRequired Fields Verify requiredfields are Missing Required populated Cost Basis InformationCusipChangeTransaction Validates Transaction CUSIP Change UOW, failsCusipChange Detected TranCodes AccountColumnsCheck Verify Accountcolumns Invalid Account are populated if the InformationbProcessTigershark flag is set to 1 AccountDataTypeCheckMarketValueVerify Market Value is Invalid Market correct type ValueBalanceColumnsPopulated Verify Balance Columns Missing Required arepopulated Balance Information BalanceDataTypeCheckCashBalance VerifyCash Balance is Invalid Cash correct type BalanceBalanceDataTypeCheckCashBalanceDate Verify Cash Balance Date InvalidCash is correct type Balance Date PositionColumnsPopulated VerifyPosition Columns Missing Positions are populated PositionDataTypeCheckAsOfDate Verify AsOfDate is correct Invalid As of Date typePositionDataTypeCheckQuantity Verify Quantity is correct InvalidQuantity type PositionDateCheckAsOfDate Verify As Of Date is no As ofDate is further than 2 months out Further than 2 Months OutTransactionAmountPopulated Verify transactions that Missing have anaction attribute Transaction of “Balance” also have Amount amountpopulated TransactionDataTypeCheckAmount Verify Amount is correctInvalid Amount type TransactionDataTypeCheckEffectiveDate VerifyEffectiveDate is Invalid Effective correct type DateTransactionDataTypeCheckQuantity Verify Quantity is correct InvalidQuantity type TransactionSignCheckQuantityNetAmount Verify Quantity andNet Invalid Quantity Amount is correctly and/or Net signed AmountObjectiveCustodianChange Verify Objective UOW Invalid Change of does nothave possible Custodian Custodian change ObjectiveRequired Fields Verifyrequired fields are Missing Required populated Objectives InformationPositionCustodianChange Verify Position UOW does Invalid Change of nothave possible Custodian Custodian change PositionDataTypeCheckEffectiveDate Verify data type Invalid Position EffectiveDate PositionDuplicateCheck Validates Position UoW Duplicate Positiondoes not have duplicate SecurityID, PositionTypeIDPositionRequiredFields Verify required fields are Missing Requiredpopulated Position Information PositionTypeValid Verify PositionTypeIDis Missing Position populated if PositionType Type ID is providedSecurityDataTypeCheckCallDate Verify data type Invalid Security CallDate SecurityDataTypeCheckDividendPayableDate Verify data type InvalidSecurity Dividend Payable Date SecurityDataTypeCheckExDivDate Verifydata type Invalid Security Ex Dividend DateSecurityDataTypeCheckFactorDate Verify data type Invalid Security FactorDate SecurityDataTypeCheckInitDate Verify data type Invalid SecurityInitial Date SecurityDataTypeCheckMatureDate Verify data type InvalidSecurity Mature Date SecurityDataTypeCheckPreviousFactorDate Verify datatype Invalid Security Previous Factor DateSecurityDataTypeCheckPriceDate Verify data type Invalid Security PriceDate SecurityDivDivDateValid Verify Dividend Invalid Securityinformation is populated Dividend properly InformationSecurityDivDivDateValid2 Verify Dividend Invalid Dividend information ispopulated Date properly SecurityDivExDivDateValid Verify DividendInvalid information is populated Reinvestment properly DateSecurityDuplicateCheck Check for duplicate Duplicate Security securityrecords SecurityIDOnCostBasis Validates CostBasis UOW Security CouldSecurityID is populated Not Be Set-up Properly SecurityIDOnPositionValidates Position UOW Missing Security SecurityID is populated ID onPosition SecurityPayableFrequencyValid Verify Missing SecurityPayableFrequencyID is Payable populated if Frequency ID PayableFrequencyis provided SecurityRequiredFields Verify required fields are MissingRequired populated Security Information SecurityShareClassValid VerifyShareClassID is Missing Security populated if ShareClass is Share ClassID provided SecurityTypeValid Verify SecurityTypeID is Missing Securitypopulated if SecurityType Type ID is providedTransactionCancellationUnmatched Verify Trade Cancellations UnmatchedTrade match existing trades in Cancellations the firmTransactionCodeValid Verify TransactionCodeID Missing is populated ifTransaction Code TransactionCode is ID providedTransactionCusipSecurityID Verify populated CUSIPs Missing Security havea ID for CUSIP SecurityID TransactionCustodianChange Verify TransactionUOW Invalid Change of does not have possible Custodian Custodian changeTransactionDataTypeCheckExecutionTime Verify data type InvalidTransaction Execution Time TransactionDataTypeCheckSettleDate Verifydata type Invalid Transaction Settle DateTransactionDataTypeCheckTradeDate Verify data type Invalid TransactionTrade Date TransactionExchangeValid Verify ExchangeID is MissingExchange populated if Exchange is ID providedTransactionPositionTypeValid Verify PositionTypeID is Missing Positionpopulated if PositionType Type ID is provided TransactionPricePopulatedVerify transactions that Missing Price have an action attribute of“PriceRequired” also have price populated TransactionQuantityPopulatedVerify transactions that Missing have an action attribute Transaction of“Reconcile” also have Quantity quantity populatedTransactionRequiredFields Verify required fields are Missing Requiredpopulated Transaction Information TransactionSolicitationValid VerifySolicitationID is Missing populated if Solicitation is Transactionprovided Solicitation ID TransactionStatusValid Verify StatusID isMissing populated if Status is Transaction Status provided ID

Examples of Functions of Some Embodiments

In some embodiments, the instant invention performs data cleansing bycorrecting or eliminating inaccurate records from a database. In someembodiments, the instant invention allows to detect so called dirty data(e.g., incorrect, irrelevant or incomplete parts of the data) to eithermodify or delete it to ensure that a given set of data is accurate andconsistent with other sets in the system.

In some embodiments, the instant invention performs historical datacleaning. For example, the inventive computer system(s)/engine(s) cananalyze the received data and perform typical fixes such as, but notlimited to:

-   -   Modify the Position Effective Date,    -   Delete Zero Position records,    -   Delete Duplicate transactions by changing the status, and    -   Modify the Transaction Effective Date.

In some embodiments, when the inventive computer system/engine findsissues with the data, it can hold the records under different validationrule categories until the issues are resolved. In some embodiments, theinstant invention provides for dynamic centralized gatekeepingfunctionality to clean data before the data received from one or moreoutside sources is imported into a company's internal databases and/orused by internal programs.

FIGS. 2-4 shows exemplary workflows in accordance with which someembodiments of the instant invention can operate. For example, in oneexemplary workflow can consist of:

1. Operation of a first computer system (e.g., Hyderabad) can includerunning query to get custodial report,

2. If any missing file or un-posted Transaction or missing multipletransactions, escalate to a second computer system (e.g., Fort WayneProd Support team), and

3. Analyzes the un-reconciled positions and accounts to determine if theissue is wide spread or one off. If it is one off issue, Hyderabadanalyzes raw file to determine issue.

Examples of some typical issues/errors with data are, but not limitedto:

-   -   Missing Transactions from Custodian    -   Wrong Effective Date    -   Invalid Position Type    -   Duplicate Transactions    -   Cusp/Symbol Change    -   Deleted Transaction    -   Corrected Transaction not reflected in Positions    -   Wrong Action on Transaction Code    -   Incorrect Manual Transaction

In some embodiments, the instant invention can, in real-time,dynamically analyzes the issue in research database(s)(feedback/learning response mechanism) and develops SQL for fix. In someembodiments, if the fix involves Position/Balance Effective date move,the instant invention can ensure the fix does not introduce newPosition/Balance reconciliation issue and the fix does not break anyperformance report. In some embodiments, affected records and SQL fixesin research database are backed up. In some embodiments, the instantinvention can have an audit log to verify that number of changes inresearch database(s) and backup tables should match. In someembodiments, the instant invention can validate SQL fixes to make surethat they do not introduce additional errors/imbalances in the data. Forexample, the instant invention can validate SQL fixes that involveTransaction Effective date move/Transaction Code changes. In someembodiments, the instant invention can implement fixes on an accountlevel, a plurality of related accounts, or a plurality of unrelatedaccounts that may have a related data issue. For example, the instantinvention can fix an incorrect price of stock over a plurality ofaccounts that belong to different custodians (e.g., brokers, banks)and/or different account owners.

Examples of RECONCILIATION Issues

Terminology:

In some embodiments, a Position means a Snapshot of shares in time, perAccount/Security/Position Type.

In some embodiments, the term Transaction(s) means details that make upPositions/Balances, Price and amount of money used to purchase shares.

In some embodiments, the term Reconcile means a total number ofTransaction shares sum up to the Position Quantity/Balance Amount as ofthat date.

In some embodiments, the instant invention can identify and flagposition records that do not balance when validated againsttransactions. In some embodiments, once the records are flagged, theinstant invention can, in real-time, dynamically research; investigatethe failed validations to determine an individual or global solution tobe applied.

Below is an example of query to get all the unreconciled positions for aparticular custodian:

Select DISTINCT    A.RecID As AccountID,    S.RecID As SecurityID,   P.RecID As Positionid,    P.EffectiveDate,    P.quantity Fromtb1Position P inner join tb1Account A on A.RecID = P.AccountID innerjoin tb1ListSource LS on LS.RecID = A.SourceID And LS.SystemCode not in(′UHA- AUE′) inner join tb1ListCustodian LC on LC.RecID = A.CustodianIDinner join tb1Position_Reconcile PR on PR.PositionID = P.RecID innerjoin tb1Security S on P.SecurityID = S.RecID  where PR.ReconcileStatusCD in(′O′) and  LC.Description=[Custodian Name] -- Analayzeindividual unreconciled positions based on AccountID/SecurityID  DECLARE @AccountID INT   DECLARE @SecurityID INT   SET @AccountID=83536 SET @SecurityID =9377   -- Position records   select * fromvwSupportPosition where AccountID=@AccountID and SecurityID =@SecurityIDORDER BY EffectiveDate   -- Transaction records   select * fromvwSupportTransaction where AccountID=@AccountID andSecurityID=@SecurityId ORDER BY EffectiveDate   --fnReconcileComparePositionTransactionWindow is the Function used to seeby now much quantity the positions records are unreconciled   -- DIFFgives us the difference and ActualDiff is the quantity expected betweenthe startperiod and endperiod   Select * ,EndPosQuantity -(StartPosQuantity + TradeQuantity)as DIFF,EndPosQuantity -StartPosQuantity as ActualDiff   fromfnReconcileComparePositionTransactionWindow(@accountID,@SecurityID,null,null)

Cash Balance Reconciliation

In some embodiments, the instant invention reconcile cash balances byanalyzing all the transaction codes received from data providers todetermine which transaction codes affect the cash balance. In someembodiments, the instant invention can review and/or provide a list oftransaction actions (tblListTransaction_Action) and flagging each actionthat affects balance with an attribute of “Balance”. Each transactioncode can be flagged with an appropriate transaction action, allowing theinvention to know which transactions should be used in the followingcalculation:

(Previous Cash Balance)+(Sum of Net Amounts for transactions whichaffect balance and occurred during the previous balance and the currentbalance)=(Current Cash Balance)

In some embodiments, the instant invention can reconcile the cash bytaking a balance window including the previous cash balance and compareto the current cash balance. By using the dates on the balance window,some embodiments can sum up the net amounts on all the transaction thatoccurred in that window and have been identified to effect cashbalances. Then add those transactions to the first balance in the windowand the result will be the amount of the current cash balance.

When a failed reconcile occurs, in some embodiments, the instantinvention can hold back all the data from a particular account thatfailed to reconcile on that particular day, and can continue to hold theaccount until a resolution is found. In some embodiments, the instantinvention can follow the data scrubbing workflows (FIGS. 2-4) todetermine if the data is missing or not being properly accounted for. Ifthe scrubbing cannot resolve the issue, in some embodiments, the instantinvention can request or communicate with computer systems of theClearing Firm or Custodian for a statement to reconcile the account.

Exemplary Common Reconciliation Issues

1) ‘Effective date’ change for position/balance

a. Balances

If the balance issues can be fixed by moving the balance date forward orbackward then update the effective date to fix un-reconciled balance(ensure that the fix does not cause issue with other balance.)

b. Positions

If the position issues can be fixed by moving the position effectivedate forward or backward then update the effective date to fixun-reconciled position (ensure that the fix does not cause issue withother Positions.)

2) Modifying Balance (based on transaction cancellation correction)

Recalculating the balances in case of issues related to cancel/correcttransactions

3) Deleting Zero positions (Zero End Pos quantity)

For example, un-reconciled zero positions can be deleted.

4) Inserting new initial transactions

If Un-reconciled positions are determined to be the first Position, theinvention can insert an initial transaction.

5) Modifying ‘Action Code’ for ‘Transaction Codes’

It can provide a supervisory review.

6) Ignoring/deleting transactions

Delete the duplicate transactions or map the duplicate transactionAction code to ‘ignore’.

7) CUSIP/symbol change

All Cusip/symbol change issues can result in a remedy ticket and oncethe solution is approved, the changes are implemented.

8) Invalid position type

For Invalid position type issues can result in a remedy ticket and oncethe solution is approved, the changes are implemented.

6.5. Mass Fixes

6.5.1. Mass cleanup and Bulk modifications

When a particular issue is determined to be impacting the data at largescale across accounts and/or custodians, queries are built and appliedto automatically identify and fix the data.

In some embodiments, the instant invention can ensure that:

1. Only the data/fields intended for the change are modified

2. System performance is not affected

3. The Guidelines for TSQL queries as listed below to be followed.

Examples of Validation Rule Engine

In some embodiments, the instant invention can provide capabilities ofrunning certain validation rules to segregate data problems into variouspredefined categories. Some fixes can be automatically put into thedata. In some embodiments, the instant invention can providecapabilities to alert/flag that identify certain issues and generateoutput that identifies them.

Examples of Validation Rules

1) Position Validation

-   -   Position/Transaction reconcile    -   Will flag position records that are out of balance    -   Each un-reconciled position record will have one of the        following flags:        -   a. Open (Out of balance)        -   b. Unresolvable (No known solution)    -   Examples        -   a. Clearing Firm A provides a position of 100 shares        -   b. Sum of last position and active transactions since the            last position is 40 shares        -   c. Position of 100 shares will be flagged as ‘Open’        -   d. Data Steward obtains and adds a transaction of 60 shares            from a Client or Custodian provided statement        -   e. Position record status is updated to ‘Cleaned’

2) Cash Balance Validation

When a failed reconcile occurs, in some embodiments, the instantinvention can hold back all the data from the account that failed toreconcile on that particular day, and can continue to hold the accountuntil a resolution is found. In some embodiments, the instant inventioncan follow the data scrubbing workflows (FIGS. 2-4) to determine if thedata is missing or not being properly accounted for. If the scrubbingcannot resolve the issue, in some embodiments, the instant invention canrequest or communicate with computer systems of the Clearing Firm orCustodian for a statement to reconcile the account.

3) Data Element Validation

In some embodiments, the instant invention can validate data elementsbased upon business rules established by a Client. For example, theinventive engine can validate and attempt to repair any data that can beprogrammatically repaired. If a record failed a validation and cannot berepaired, the record will be held back for further investigation. Allfailed validations can be identified and logged for auditing. In someembodiments, the instant invention can provide a functionalities todynamically examine the data feed rules to see if the issue can be fixedglobally in the data feed. If the issue is isolated and a one-off, theinstant invention can request or communicate with computer systems ofthe Clearing Firm or Custodian for a statement to reconcile the account.Once the record is repaired and re-validated, the data will be deliveredto the Client via the IDM.

In some embodiments, Data Element Validations can consist of thefollowing:

-   -   Able to audit any data    -   Rules based validation    -   Capable of running data validation rules on a given unit of work        (e.g. an account or security). If a transaction is received or        updated, the account will be checked again.    -   Data record will be marked accordingly regarding success or        failure for each validation rule    -   Records will not be passed to clients until they have        successfully passed all validations    -   Data scrubbing engine also contains a repair process    -   Repair process will handle cases where a known data issue can be        reliably and accurately corrected.

In some embodiments, the instant invention can offer an ability tocustomize validation rules to business requirements. In someembodiments, the customized rules can be Custodian or Security typebased wherever needed.

Security Master Validation (CUSIP and Symbol Validation)

In some embodiments, the instant invention can validate for correctCUSIPS and symbols. If the symbol is the same as the CUSIP, records canbe held back from being released the symbol or CUSIP is corrected bycontacting the Custodian, Clearing Firm, or use available resources. Insome embodiments, the instant invention can identify securities that aremissing the symbol or CUSIP, and flagged those for further checking thesymbol or CUSIP.

Posting Considerations Validation

In some embodiments, the instant invention can handle rules basedvalidations related to the posting of data to an externaldatabase/computer system. In some embodiments, the inventive computersystems and methods of the instant invention can utilize validations toprevent the loading of incorrect custodial data. In some embodiments,the inventive computer systems and methods of the instant invention,depending upon the data type of external source data and/or at user'sdiscretion, process a particular data type through the cleansing enginebut not hold the data from posting to the Data Warehouse and in turn theIDM. For example, the above procedure can be useful if a particularfield is required for posting while other fields are held back fromposting until such time as data anomalies identified by the scrubbingengine(s) (identified as “Stingray”, “Tigershark” in Figures) have beencorrected.

Error Log

In some embodiments, the instant invention can provide an error log tovalidate data quality. In one example, the error log can consist of theaccount/security that failed the validation as well as the validationthat failed. In another example, the log can consist of records that arecurrently in a fail state; once the record is repaired and revalidatedthe record will be removed from the error log table.

Remedy

In some embodiments, the instant invention can provide a remedy systemfor tracking purposes.

Issue Logging System

Each data raise is logged in the Remedy/Tracking system.

Exemplary Guidelines for writing TSQL queries

1. Do not leave queries running unattended.

2. Do not leave them running for more than 10 minutes unless authorized(full run of spReconcile_Positions_Calc is authorized to be run once aweek on any firm, no more)

3. Do NOT restart a script that has been forcibly killed (severe erroroccurred/query window has been disconnected/etc.) until the script hasbeen reviewed.

4. If you have done a BEGIN TRANSACTION, you need to make sure that youhave Committed or ROLLBACK the transaction.

Note; it is possible to have more than one level of transaction open. Ifthis is the case, you need to make sure that you have committed as manytimes as you began the transactions. If SELECT @@TRANCOUNT returnsanything other than 0, then you still have a transaction open.

Exemplary SQL Mass cleanup queries Review process

A following list needs to be reviewed before being run:

1. OUTER/CROSS APPLY

2. WHILE/CURSOR loops (batch processing is fine if you're doing 100's to1000's of records at a time, one at a time loops are avoided)

3. Subs-elects containing a view/more than 3 levels of sub-selects

4. Temp tables with over 1 million rows

Examples of Modifying Fields

1. Transaction Effective Dates should be changed only after aconfirmation or if it is a known issue.

2. Action Codes for Tran Codes should not be modified and a remedyshould be raised when needed.

3. Position Effective Date can be automatically modified within acertain predetermine range of days.

Testing

Reconciliation check

In some embodiments, the instant invention can ensure that the fixapplied corrects the issue in totality and does not give a partialsolution. In some embodiments, the check can be done in two ways basedon where the fix is applied

-   -   Firm fix: Once the fix is applied in the firm, the check should        be simple enough to see if the position/balance which was not        reconciled before is fixed.    -   Conditional fix: The records in error are marked with a        particular identifier (e.g., statusid 3) and once the solution        is found and applied, the statusid should change to 2 and the        corresponding records should be released into destination        database. In some embodiments, the records (fixed records and/or        records that were previously identified as compliant) may need        to be reprocessed for the records to be released.

Impact on Reports

In some embodiments, the instant invention can provide reportsregarding, but not limited to, errors identified and/or fixes. In someembodiments, the instant invention can, in real-time, dynamically checkfor the accuracy of the fix with some scripts to see if they have apositive/negative impact on the reports. In some embodiments, it is notnecessary that a fix that breaks a report is always a bad fix because itcould be a change that might have to be incorporated in the reports.

Table 3 shows examples of database objects that can be utilized in someembodiments of the instant invention.

TABLE 3 Database Object Detail tblListCustodian Static table forCustodians tblListSource Static table for Data sourcestblListThirdPartyMoneyManager Static table for TAMP datatblListBalanceType Static table for Balance types tblListPosition TypeStatic table for Position types tblPosition Table holding all theposition records tblBalance Table holding all the balance recordstblTransaction Table holding all the transaction records tblAccountTable holding all the account level details. tblSecurity Table holdingall the security level details. tblPosition_Reconcile Table which holdsthe reconcile status of the position records tblBalance_Reconcile Tablewhich holds the reconcile status of the balance records tblPosition_Calcholds all the unreconciled position details. vwsupportPosition View forPosition table with extra details for the purpose of analysisvwsupportBalance View for Balance table with extra details for thepurpose of analysis vwsupportTransaction View for transaction table withextra details for the purpose of analysisfnReconcileComparePositionTransactionWindow Function used to analyzePosition/Balance reconciliation

Table 4 shows examples of validation engine objects that can be utilizedin some embodiments of the instant invention.

TABLE 4 Validation Engine Object Detail vwUnitOfWorkAccountFailures Viewgiving details pertaining to validation rulevwUnitOfWorkAccountFailuresDetail View giving the exact record id inaddition to the details already given by the above view pertaining tovalidation rule tblImport_[Firm]_Account Account data in ValidationEngine/database tblImport_[Firm]_Security Security data in ValidationEngine/database tblImport_[Firm]_Position Position data in ValidationEngine/database tblImport_[Firm]_Balance Balance data in ValidationEngine/database tblImport_[Firm]_Transaction Transaction data inValidation Engine/database

FIGS. 7-9 show exemplary workflows for some embodiments of the instantinvention as described herein.

In some embodiments, the inventive systems and methods of the instantinvention can be utilized in conjunction with processes and/or dataformats described in U.S. Pat. Nos. 7,653,564; 7,689,489; U.S. PatentPub. No. 20080040610; U.S. Patent Pub. No. 20090006267; whose specificdisclosures of data processing and/or data formats are herebyincorporated herein by reference for all purposes associated with suchdata processing and/or data formats.

Illustrative Operating Environments of Some Embodiments of the InstantInvention.

FIG. 5 illustrates one embodiment of an environment in which the presentinvention can operate. However, not all of these components may berequired to practice the invention, and variations in the arrangementand type of the components may be made without departing from the spiritor scope of the invention. In some embodiment, the system hosts a largenumber of members and concurrent transactions. In other embodiments, thesystem is based on a scalable computer and network architecture thatincorporates varied strategies for assessing the data, caching,searching, and database connection pooling. An example of the scalablearchitecture is an architecture that is capable of operating multipleservers.

In some embodiments, client devices 502-504 include virtually anycomputing device capable of receiving and sending a message over anetwork, such as network 505, to and from another computing device, suchas servers 506 and 507, each other, and the like. In embodiments, theset of such devices includes devices that typically connect using awired communications medium such as personal computers, multiprocessorsystems, microprocessor-based or programmable consumer electronics,network PCs, and the like. In embodiments, the set of such devices alsoincludes devices that typically connect using a wireless communicationsmedium such as cell phones, smart phones, pagers, walkie talkies, radiofrequency (RF) devices, infrared (IR) devices, CBs, integrated devicescombining one or more of the preceding devices, or virtually any mobiledevice, and the like. Similarly, in some embodiments, client devices502-504 are any mobile device that is capable of connecting using awired or wireless communication medium such as a PDA, POCKET PC,wearable electronic device (such as cellular phone, smart phone, orother equivalent mobile devices), and any other device that is equippedto communicate over a wired and/or wireless communication medium.

In some embodiments, each client device within client devices 502-504includes a browser application that is configured to receive and to sendweb pages, and the like. In embodiments, the browser application isconfigured to receive and display graphics, text, multimedia, and thelike, employing virtually any web based language, including, but notlimited to Standard Generalized Markup Language (SMGL), such asHyperText Markup Language (HTML), a wireless application protocol (WAP),a Handheld Device Markup Language (HDML), such as Wireless MarkupLanguage (WML), WMLScript, JavaScript, and the like. In embodiments,computer systems of the instant invention is programmed in either Javaor .Net.

In embodiments, client devices 502-504 are further configured to receivea message from the another computing device employing another mechanism,including, but not limited to email, Short Message Service (SMS),Multimedia Message Service (MMS), instant messaging (IM), internet relaychat (IRC), mIRC, Jabber, and the like.

In embodiments, network 505 is configured to couple one computing deviceto another computing device to enable them to communicate. Inembodiments, network 105 is enabled to employ any form of computerreadable media for communicating information from one electronic deviceto another. Also, in embodiments, network 505 includes a wirelessinterface, and/or a wired interface, such as the Internet, in additionto local area networks (LANs), wide area networks (WANs), directconnections, such as through a universal serial bus (USB) port, otherforms of computer-readable media, or any combination thereof. Inembodiments, on an interconnected set of LANs, including those based ondiffering architectures and protocols, a router acts as a link betweenLANs, enabling messages to be sent from one to another.

Also, in some embodiments, communication links within LANs typicallyinclude twisted wire pair or coaxial cable, while communication linksbetween networks may utilize analog telephone lines, full or fractionaldedicated digital lines including T1, T2, T3, and T4, IntegratedServices Digital Networks (ISDNs), Digital Subscriber Lines (DSLs),wireless links including satellite links, or other communications linksknown to those skilled in the art. Furthermore, in embodiments, remotecomputers and other related electronic devices could be remotelyconnected to either LANs or WANs via a modem and temporary telephonelink. In essence, in embodiments, network 505 includes any communicationmethod by which information may travel between client devices 502-504,and servers 506 and 507.

In some embodiments, clients can query databases utilizing SQL(Structured Query Language) or Transact-SQL (T-SQL), programminglanguages designed for managing data in database management systems. Insome embodiments, T-SQL can include procedural programming, localvariables, various support functions for string processing, dateprocessing, mathematics, etc. and changes to the DELETE and UPDATEstatements.

FIG. 6 shows another exemplary embodiment of the computer and networkarchitecture that can support the disclosed systems and methods of theinstant invention. The client devices 602 a, 602 b thru 602 n shown eachcomprises a computer-readable medium, such as a random access memory(RAM) 608 coupled to a processor 610. The processor 610 executescomputer-executable program instructions stored in memory 608. Suchprocessors comprise a microprocessor, an ASIC, and state machines. Suchprocessors comprise, or are in communication with, media, for examplecomputer-readable media, which stores instructions that, when executedby the processor, cause the processor to perform the steps describedherein. Embodiments of computer-readable media include, but are notlimited to, an electronic, optical, magnetic, or other storage ortransmission device capable of providing a processor, such as theprocessor 610 of client 602 a, with computer-readable instructions.Other examples of suitable media include, but are not limited to, afloppy disk, CD-ROM, DVD, magnetic disk, memory chip, ROM, RAM, an ASIC,a configured processor, all optical media, all magnetic tape or othermagnetic media, or any other medium from which a computer processor canread instructions. Also, various other forms of computer-readable mediatransmit or carry instructions to a computer, including a router,private or public network, or other transmission device or channel, bothwired and wireless. The instructions comprise code from anycomputer-programming language, including, for example, C, C++, C#,Visual Basic, Java, Python, Perl, and JavaScript.

Client devices 602 a-n also comprise a number of external or internaldevices such as a mouse, a CD-ROM, DVD, a keyboard, a display, or otherinput or output devices. Examples of client devices 602 a-n are personalcomputers, digital assistants, personal digital assistants, cellularphones, mobile phones, smart phones, pagers, digital tablets, laptopcomputers, Internet appliances, and other processor-based devices. Ingeneral, a client device 602 a are any type of processor-based platformthat is connected to a network 206 and that interacts with one or moreapplication programs. Client devices 602 a-n operate on any operatingsystem capable of supporting a browser or browser-enabled application,such as Microsoft™, Windows™, or Linux. The client devices 202 a-n showninclude, for example, personal computers executing a browser applicationprogram such as Microsoft Corporation's Internet Explorer™, AppleComputer, Inc.'s Safari™, Mozilla Firefox, Google Chrome, and/or Opera.

Through the client devices 602 a-n participants 612 a-n communicate overthe network 606 with the system. As shown in FIG. 6, server devices 604and 613 are also coupled to the network 606.

For the purposes of this disclosure, a computer readable medium is amedium that stores computer data/instructions in machine readable form.By way of example, and not limitation, a computer readable medium cancomprise computer storage media as well as communication media, methodsor signals. Computer storage media includes volatile and non-volatile,removable and non-removable media implemented in any method ortechnology for storage of information such as computer-readableinstructions, data structures, program modules or other data. Computerstorage media includes, but is not limited to, RAM, ROM, EPROM, EEPROM,flash memory or other solid state memory technology; CD-ROM, DVD, orother optical storage; cassettes, tape, disk, or other magnetic storagedevices; or any other medium which can be used to tangibly store thedesired information and which can be accessed by the computer.

Further, the present invention may, of course, be implemented using anyappropriate computer readable medium, computer system(s), computerhardware and/or computer software. In this regard, those of ordinaryskill in the art are well versed in the type of computer hardware thatmay be used (e.g., a mainframe, a mini-computer, a personal computer(“PC”), a network (e.g., an intranet and/or the Internet)), the type ofcomputer programming techniques that may be used (e.g., object orientedprogramming), and the type of computer programming languages that may beused (e.g., C++, Basic). The aforementioned examples are, of course,illustrative and not restrictive.

In some embodiments, the instant invention includes acomputer-implemented method that includes at least: specificallyprogramming at least one computer system to perform at least thefollowing: automatically obtaining input financial data from at leastone source; automatically determining a first plurality of units of workthat the input financial data can be organized into; automaticallyimporting the input financial data into at least one database based, atleast in part, on the first plurality of units of work; automaticallyvalidating the imported input financial data, where the validatingincludes at least: identifying, in the imported input financial data, asecond plurality of deficient units of work based on a third pluralityof predefined rules, where each deficient unit of work is a unit of workhaving at least one first current data error; analyzing, based at leastin part on research information in at least one first research database,the at least one first current data error to determine at least onefirst current corrective action to remedy the at least one first currentdata error, where the research information comprises historicalinformation about at least one first previous data error and at leastone first previous corrective action that remedied the at least onefirst previous data error; and verifying that the at least one firstcurrent corrective action does not result in at least one of: i) atleast one additional deficient unit of work, ii) at least one additionaldata error, and iii) at least one change in at least one predefined datareport; and automatically executing the at least one first currentcorrective action to remedy the at least one first current data error.

In some embodiments, each unit of work from the first plurality of unitsof work represents an account or a financial asset.

In some embodiments, the step of the automatically validating theimported input financial data can include segregating each deficientunit of work from the second plurality of deficient units of work intopredefined categories.

In some embodiments, the third plurality of predefined rules caninclude: i) at least one first standard rule that is a required rule,and/or ii) at least one optional rule.

In some embodiments, the third plurality of predefined rules includesrules associated with at least one of: i) position validation, ii) cashbalance validation, iii) data element validation, iv) securityvalidation, and v) posting considerations validation.

In some embodiments, the at least one first current data error ispersonal to a particular unit of work.

In some embodiments, the at least one first current data error isassociated with the common among the second plurality of deficient unitsof work.

In some embodiments, the step of the automatically validating theimported input financial data can further include: withholding fromposting each deficient unit of work for which a corrective action hasnot been determined.

In some embodiments, the step of the automatically validating theimported input financial data can further include: automatically markingeach deficient unit of work when posting the imported input financialdata so as to visually identify each deficient unit of work.

In some embodiments, the step of the automatically marking can furtherinclude: visually identifying each deficient unit of work based at leastin part on one of: i) at least one first type of data error, and ii) atleast one first pattern of data errors.

In some embodiments, the instant invention includes a computer systemthat includes at least the following components: a non-transient memoryhaving at least one region for storing computer executable program code;and at least one processor for executing the program code stored in thememory, where the program code includes at least: code to automaticallyobtain input financial data from at least one source; code toautomatically determine a first plurality of units of work that theinput financial data can be organized into; code to automatically importthe input financial data into at least one database based, at least inpart, on the first plurality of units of work; code to automaticallyvalidate the imported input financial data, where the code to validateincludes at least: code to identify, in the imported input financialdata, a second plurality of deficient units of work based on a thirdplurality of predefined rules, where each deficient unit of work is aunit of work having at least one first current data error; code toanalyze, based at least in part on research information in at least onefirst research database, the at least one first current data error todetermine at least one first current corrective action to remedy the atleast one first current data error, where the research informationcomprises historical information about at least one first previous dataerror and at least one first previous corrective action that remediedthe at least one first previous data error; and code to verify that theat least one first current corrective action does not result in at leastone of: i) at least one additional deficient unit of work, ii) at leastone additional data error, and iii) at least one change in at least onepredefined data report; and code to automatically execute the at leastone first current corrective action to remedy the at least one firstcurrent data error.

While a number of embodiments of the present invention have beendescribed, it is understood that these embodiments are illustrativeonly, and not restrictive, and that many modifications may becomeapparent to those of ordinary skill in the art. Further, any stepsdescribed herein may be carried out in any desired order (and any stepsmay be added and/or deleted).

What is claimed is:
 1. A computer-implemented method, comprising:specifically programming at least one computer system to perform atleast the following: automatically obtaining input financial data fromat least one source; automatically determining a first plurality ofrules by which the input financial data can be organized based on;automatically importing the input financial data into at least onedatabase based, at least in part, on the first plurality of rules. 2.The computer-implemented method of claim 1, wherein each unit of workfrom the first plurality of rules represents an account or a financialasset.
 3. A computer system, comprising: a non-transient memory havingat least one region for storing computer executable program code; and atleast one processor for executing the program code stored in the memory,wherein the program code comprising: code to automatically obtain inputfinancial data from at least one source; code to automatically determinea first plurality of rules that the input financial data can beorganized upon; and code to automatically import the input financialdata into at least one database based, at least in part, on the firstplurality of rules.
 4. The computer system of claim 3, wherein each unitof work from the first plurality of rules represents an account or afinancial asset.